-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Allow setting a different user class for backend users #6329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #6329 +/- ##
==========================================
- Coverage 89.35% 89.31% -0.05%
==========================================
Files 961 961
Lines 20195 20210 +15
==========================================
+ Hits 18046 18051 +5
- Misses 2149 2159 +10 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
This seems like a good idea to me. This separation could be useful for some marketplace stores we work on as well. |
|
@jarednorman wanted to do this for a long time, and never got the time until I was able to delegate 😅 |
…o user_class. Update initializer template, menu conditions, controllers, views, and helper.
…_sqlite early for sqlite3 v2
…lick) and update admin docs to use Spree.admin_user_class
Disclaimer: this PR was entirely written by codex under my guidance, for good or for bad 😊
Summary
This change will open to having separate classes for customers and backend operators, this brings the following advantages:
Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:
The following are not always needed: